Skip to content

Conversation

@safern
Copy link
Member

@safern safern commented Feb 24, 2021

Fixes: #48659

I also added batched: true as this was running for every single commit.

Also, added pr: none as at the moment we don't want to run them on PRs because of time constraints. @jepetty is doing some more work to enable native richnav, once we get that we will work to enable this on PRs so that people can use richnav to do PR reviews.

@ghost
Copy link

ghost commented Feb 24, 2021

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@ghost
Copy link

ghost commented Feb 24, 2021

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes: #48659

I also added batched: true as this was running for every single commit.

Also, added pr: none as at the moment we don't want to run them on PRs because of time constraints. @jepetty is doing some more work to enable native richnav, once we get that we will work to enable this on PRs so that people can use richnav to do PR reviews.

Author: safern
Assignees: -
Labels:

area-Infrastructure

Milestone: -

Copy link
Contributor

@jepetty jepetty left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love it! Thanks, @safern!

@safern
Copy link
Member Author

safern commented Feb 24, 2021

Merging as this doesn't affect CI.

@safern safern merged commit eb03e0f into dotnet:master Feb 24, 2021
@safern safern deleted the FixupRichnavTriggers branch February 24, 2021 19:58
@ghost ghost locked as resolved and limited conversation to collaborators Mar 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RichNav should not be running for docs only changes

3 participants